One-way Synchronization

In a one-way synchronization you specify one system, typically your ITS, as the master. Changes made to issue records on the master system are reflected on the other system, but not vice versa, when the synchronization is run. For example, if you specify your ITS as the master system, data from the ITS issue records is written to the corresponding issue records in AccuWork. Changes made to issue records in AccuWork are not reflected in your ITS and, in fact, might be overwritten with changes made in the ITS the next time the records are synchronized. If you use AccuWork as the master, change package information, including affected files, version, and basis version information, is also written to your ITS during a one-way synchronization.

The behavior of a synchronization pattern defined with a one-way synchronization type is similar to that of AccuBridge. Typical uses of a one-way synchronization pattern include:

• Overriding the two-way synchronization type specified for a synchronization pattern for individual field mappings for fields whose values you do not want updated.
• Initial population of one issue tracking system with issue records from another.

Two-way Synchronization

The two-way synchronization type is completely bidirectional: changes made to issue records in one system are updated on the other when the synchronization is run. The most recent data at the time of the synchronization is used to update the record on the other system. Change package information is written from AccuWork to your ITS.

Note that any validation logic or constraints that have been defined for a field in one system should also be defined in the other. For example, if you have defined the Assigned To field in your AccuWork schema as a required field, you should ensure that your ITS schema enforces that rule for whatever field you mapped to Assigned To.

Synchronization patterns are defined with a two-way synchronization type by default.

Synchronization Type Can Be Overridden

The synchronization type specified in the synchronization pattern applies to all the field mappings defined for the mapping definition associated with the synchronization pattern. If you want, you can override the synchronization type for individual field mappings. See Synchronization Types Inherited from Synchronization Pattern for more information.